I can't comment on line 7, but Sales should be Sales, since apps are all bold.

In lines 10-11, is "materials, liquids, or foods' necessary? Or could it just be "businesses that sell large quantities of items, where the orddered quantity may differ from the delivered quantity."

Just seems odd unless there's a specific reason.

Also, i recommenda dding an example admonition to showcase the reason. Like :

Example: A company sells fresh produce. A customer buys 50 heads of lettuce, but there are only 48 available heads when delivery is made. The customer only received 48, then 2 later. So you can explain that they are invoiced for the 48, and then invoiced separately for the additional 2 after they are received.

Just an idea!

Just to emphasize this distinction - this is majorly important. Also, if there is a good place to link the text "updated on their product forms: - I would add that.

Line 46 : Sales

54056 - app names should be bold.

Seealso is typically just the doc, no intro sentence needed

I think you can link to the specific related doc sections for the various create an invoice options: Regular invoice, Down payment (percentage) or Down payment (fixed amount).

I find it odd that both the columns display "0"- Is this normal? Wouldn't we want to show a difference, delivered X and ordered Y? Just looks off. Also, remove the arrows.

I would have the example go beneath and nested in with the example.

This is just a suggestion, to just make them stand out more clearly and get irght into it up front =)
I couldn't edit the lines below for some reason, so just remove everything after the above, until the example.

I beieve we write out numbers under ten (maybe twenty)? Also, is this a "rule" or an "option"? Just want to be sure the right word is used. I didn't think of this yesterday!

Again - I think this is an "option" rather than a "rule". I only say this, since in Payroll, there are rules, which work a specific way, as opposed to options you select. So the wording is important - if this is a "rule" or an "option". From looking at it, I THINK its an option - but you can check with the developers or osmeone with more knoelwdge of sales, if it is in fact a "rule".

If we didn't have "rules" in the database that affect my app scopoe, I woudlnt' even have htought about this =D

Just more visual emphasis

Since the warning is only referencing the second bullet point, I woudl have this nexted under that bullet point (just indent it 2 spaces each line)

Again, check if this is a rule or just an option.

I see "Invoiced quantity" as zero. Wouldn't we want to see this as 12?

Also, for this example. it might be good ot see delivered "8", ordered "12" and "invoiced 8" to see what you'd expect to see. Also, I woudl move this below, so there is no tet beneath it - then the image will match all the text above. I try to ensure images are at the end of a section fo text, with nothing beneath it - so people don't think they are done with whatever the steps are. Kind of like a hard stop, "This is whta it looks like if you did everything right" (Of course, for all the important steps in between, I woudl addd more, but in general, if only one image is needed, I ususally put it at the end, amnd make sure all the info in the text above is what is sohwn, which is why I suggest aving osmehting in the "invoices" section)

For this image, you could crop out the right and lower side, so you just see the important part - example:

(I couldnt get the drop down to show, but you get the idea!=) I zoom in to make sure everythign is as big as it can be, before cropping or resizing)

I don't believe we want to use any italics in a heading/sub-heading. You can change this to just "Workflow" or "Invoice ordered quantity workflow".

I think this can be a Tip - so if I understand correctly, if they have the Inventory app, they don't really need to update the quantities- it is updated automatically when delivered? I'd elaborate that, just so people know,. It sound slike a tip because if they have Inventory, there's less to do/it's more automated? Disregard if I am incorrect!

Use the same concept as the previous "use case" section - whatever you decide!